Use exportsOverride to rename target folders #138
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- exportOverride can now use an extended definition that has "packageName" naming convention which is run through Handlebars with package's metadata (so one can install to i.e. "js/jquery-2.1.1" based on metadata of Bower packages) - added dependencies to Q and Handlebars
- added unit tests for new functionality, fixed JSHint warnings
- "component.json" files were not added in previous commit due to .gitignore
|
@yatskevich Is this gonna be merged anytime soon? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I needed to be able to easily customize target folder names in my project to follow convention that uses version numbers in folder names, so that i.e.
"jquery": "~2.1.1"(frombower.json) gets installed to "js/jquery-2.1.1" (and not as now to "js/jquery"). This change extendsexportsOverrideconfiguration option withpackageNamenaming convention which is run through Handlebars with package's metadata (so one can install to i.e. "js/jquery-2.1.1" based on metadata of Bower packages). I also added dependencies to Q and Handlebars to make it work. You can find more details in updated Readme file.